Check if this issue is valid — if so, understand the root cause and fix it. At packages/agent/src/workflows/verification-workflow.ts, line 244:

<comment>Last-resort fallback returns a different problem without re-verifying it, but reuses prior gate results. This can emit inconsistent result payloads where verification evidence does not belong to the returned problem.</comment>

<file context>
@@ -183,6 +214,55 @@ export async function* runVerificationWorkflow(
+  }
+
+  const problem = withDeterministicGeneratorMarker(fallback);
+  const verification = { ...input.verification, candidate_id: problem.candidate_id };
+  assertVerificationInvariants(verification);
+  return { problem, verification };
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At packages/agent/src/policies/acceptance-policy.ts, line 17:

<comment>Configurable maxAttempts is inconsistent with invariant I-V5 fixed at 3, causing runtime invariant failures when maxAttempts > 3. Align policy limit with invariant or update invariant to use same configured cap.</comment>

<file context>
@@ -6,20 +6,33 @@ export interface AcceptancePolicy {
   return {
     decide(gates, attemptCount) {
-      if (attemptCount > 3) return "rejected";
+      if (attemptCount > maxAttempts) return "rejected";
 
       const byStep = new Map(gates.map((gate) => [gate.step, gate]));
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At packages/agent/src/schemas/source-problem.schema.ts, line 68:

<comment>I-S4 check incorrectly forbids all null explanations. This will fail legitimate dataset-30 rows that are explicitly allowed by domain invariants.</comment>

<file context>
@@ -54,3 +54,21 @@ export const SourceProblemSchema = z.object({
+  if (/\\(?:d?frac|sqrt|cdot|left|right|pi|pm)/u.test(problem.question_text)) {
+    throw new Error(`I-S3 violated: source problem ${problem.item_id} question_text must be normalized plain text`);
+  }
+  if (problem.explanation_text === null || problem.explanation_text.trim().length === 0) {
+    throw new Error(`I-S4 violated: source problem ${problem.item_id} needs explanation_text`);
+  }
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At packages/agent/src/schemas/source-problem.schema.ts, line 65:

<comment>I-S3 regex is stricter than spec and will fail valid LaTeX questions. It should only block non-normalized fraction commands.</comment>

<file context>
@@ -54,3 +54,21 @@ export const SourceProblemSchema = z.object({
+  if (problem.achievement_standard === null || problem.achievement_standard.trim().length === 0) {
+    throw new Error(`I-S2 violated: source problem ${problem.item_id} needs achievement_standard`);
+  }
+  if (/\\(?:d?frac|sqrt|cdot|left|right|pi|pm)/u.test(problem.question_text)) {
+    throw new Error(`I-S3 violated: source problem ${problem.item_id} question_text must be normalized plain text`);
+  }
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At packages/agent/src/tools/latex-formatter.ts, line 20:

<comment>`\pm` expansion is algebraically incorrect because it removes the left operand. This can produce wrong candidate roots/answers for SymPy verification.</comment>

<file context>
@@ -4,6 +4,50 @@ export function formatLatex(value: string): string {
+    .replace(/\\leq?|≤/g, "<=")
+    .replace(/\\geq?|≥/g, ">=")
+    .replace(/\\pi/g, "pi")
+    .replace(/\\pm\s*([^\s,]+)/g, "-$1, $1")
+    .replace(/\^/g, "**");
+  expression = extractEquationText(expression)
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At packages/web/hooks/use-verification-stream.ts, line 212:

<comment>Gate status is not validated against the 4-state contract, so invalid payloads are treated as valid results. This can hide the “기호 검증 불가” signal instead of failing the stream payload.</comment>

<file context>
@@ -188,6 +203,15 @@ function parsePreview(raw: unknown): string | null {
+  const step = asString(o.step);
+  const status = asString(o.status);
+  if (step === null || status === null) return null;
+  return { step, status };
+}
+
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At packages/agent/src/steps/intent-extraction.ts, line 124:

<comment>Fallback intent incorrectly preserves only the first requested dimension. This can make objective mapping/verification ignore user-selected preserve constraints beyond index 0.</comment>

<file context>
@@ -116,3 +112,15 @@ function buildSeedIntent(
+  return descriptions.map((description, index) => ({
+    id: String.fromCharCode(65 + index),
+    description,
+    must_preserve: index === 0,
+  }));
+}
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At packages/agent/src/config/env.ts, line 40:

<comment>JSDoc for `last-resort` mode says "currently behaves like `first`" but the implementation treats it differently: generation skips template first (unlike `first`) and final-result fallback is already gated on `last-resort`. Stale docs risk misinforming configuration decisions.</comment>

<file context>
@@ -29,10 +34,19 @@ export const EnvSchema = z.object({
+
+  /** `first` = template short-circuits LLM when refs exist (current behavior).
+   *  `off` = always go through LLM generator path; never substitute template.
+   *  `last-resort` = placeholder, currently behaves like `first` (see TODO 1-1a). */
+  DETERMINISTIC_FALLBACK: z
+    .enum(["off", "last-resort", "first"])
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At docs/specs/domain.md, line 171:

<comment>Stale name `independent_resolve` conflicts with `re_solve` in same invariant — gate[4] step is `re_solve` per GateResult.</comment>

<file context>
@@ -168,7 +168,7 @@ type HumanFailureReason = {
 - (I-V2) `overall == "verified"`는 `gates[3] (sympy_verify).status == "passed"` **and** `gates[5] (objective_map).status == "passed"` 일 때만 가능 (결정론 게이트).
 - (I-V3) `gates[1] (intent)`와 `gates[2] (generate)`가 passed라도 `gates[3] (sympy_verify)`가 failed면 `overall != "verified"` (D-1: LLM은 정답 판단 X).
-- (I-V4) `overall == "warning"`은 SymPy는 통과했으나 `independent_resolve`(gates[4])가 불일치할 때만 사용 — 사용자에게 *주의* 라벨로 노출.
+- (I-V4) `overall == "warning"`은 SymPy가 `passed` 또는 `unverified`인 상태에서 `independent_resolve`(gates[4])가 불일치했거나, 비결정 가능(non-decidable) 게이트가 `unverified`일 때 사용 — 사용자에게 *주의* 라벨로 노출. 단, 재시도 상한의 최종 attempt에서도 `re_solve` 불일치가 지속되면 `warning`이 아니라 `rejected`다.
 - (I-V5) `attempt_count > 3`이면 강제 `overall == "rejected"` (Q-5 잠정 정책, D-9에서 확정 예정).
 
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At packages/agent/src/steps/intent-extraction.ts, line 72:

<comment>`dimensions_source` provenance is inaccurate when strategy is null but request dimensions are provided. This weakens observability for fallback quality analysis.</comment>

<file context>
@@ -69,6 +69,7 @@ export async function extractIntent(
   } catch (err) {
     const fallback = buildSeedIntent(input.request, input.strategy, input.refs);
     assertIntentInvariants(fallback);
+    const dimensionsSource = input.strategy === null ? "guessed" : "strategy";
     return {
       data: fallback,
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At packages/agent/src/steps/objective-mapping.ts, line 202:

<comment>Technique gate for non-conceptual mode is stricter than schema semantics; it requires all required techniques instead of at least one. This can incorrectly reject otherwise valid generations.</comment>

<file context>
@@ -140,7 +169,70 @@ function evaluateDeterministically(input: ObjectiveMappingInput): Array<{ code:
+        message: `Candidate techniques ${formatTechniqueList(used)} do not overlap required or related techniques ${formatTechniqueList(related)}`,
+      });
+    }
+  } else if (missingRequired.length > 0) {
+    failures.push({
+      code: "technique_mismatch",
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At packages/agent/src/tools/answer-equivalence.ts, line 65:

<comment>New answer-equivalence decision flow is duplicated across two functions, creating avoidable divergence risk. Extract shared comparison logic and pass context-specific messages/inputs.</comment>

<file context>
@@ -3,10 +3,123 @@ import type { MathEngineClient } from "./math-engine-client.js";
+  return { status: "undecidable", reason: withSkippedReasons("math-engine could not compare the answers", debug) };
+}
+
+export async function decideAnswerMatchesSolutions(
+  mathEngine: MathEngineClient,
+  answer: string,
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At packages/agent/src/server/sse/progress-stream.ts, line 73:

<comment>Forwarding driver error events in parallel mode causes the frontend to abort before merged results arrive. A single failed driver run can hide successful candidates from other runs.</comment>

<file context>
@@ -32,3 +32,66 @@ export async function pipeProgressToSse(
+        collected.push(event);
+        continue;
+      }
+      if (event.type === "error") forwardedError = true;
+      await writeWire(event);
+    }
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At packages/agent/src/server/routes/generate.ts, line 23:

<comment>Route hard-caps `request.count` to 3, violating the API contract and silently returning fewer problems than requested.</comment>

<file context>
@@ -18,8 +20,12 @@ export function createGenerateRoute(deps: VerificationWorkflowDeps, options?: Ru
     zValidator("json", GenerateRequestSchema),
     (c) => {
       const request = c.req.valid("json");
+      const count = Math.min(Math.max(request.count, 1), MAX_PARALLEL_GENERATIONS);
       return streamSSE(c, async (stream) => {
-        await pipeProgressToSse(stream, runVerificationWorkflow(deps, request, options));
</file context>